feat: add lambda container image support#95
Conversation
Signed-off-by: Tony <theton369@gmail.com>
|
Hey @djfdyuruiry, can you please have a look when you have time. Our team really like this package but it doesn't support Lambda Container Image so we updated it. |
Hi @k0nkupa - thanks for this PR. There are some unrelated issues that are causing the build to fail in GitHub Actions. I have fixed these issues in release v2.5.4 - https://github.com/djfdyuruiry/ts-lambda-api/releases/tag/v2.5.4 If you can update your PR with the lastest changes on |
Hey mate, I’ve updated the PR with the latest changes from master/v2.5.4. I also verified locally that:
|
|
Thanks for resolving that conflict, I will roll this into a new release. |
|
This has been included in the v2.5.5 release
|
2 participants
Summary
Add first-class Lambda container-image support to
ts-lambda-api.This PR introduces native Lambda HTTP event support, adds a
createHandler()API for exporting standard Lambda handlers, makes controller discovery recursive/deduplicated, and updates the README to document container-image deployment as a supported path.Changes
ApiLambdaAppcreateHandler()for standard Lambda handler exportsWhy
Container-image deployment itself was not the real problem. The friction came from missing package-level support, which forced downstream apps to manually reshape events and enumerate controller paths.
This PR moves that logic into the library and makes container-image usage a supported, tested path.
Validation
Ran successfully:
yarn buildyarn build-testsscripts/runTests.shTests cover:
createHandler()